@Kidev install-qt-action already passes --autodesktop, it's just that it doesn't typically work if you specify aqtsource as you were probably doing for testing. The logic for when it passes in the parameter is determined by:

const isAutodesktopSupported = async (): Promise<boolean> => {
  const rawOutput = await getPythonOutput("aqt", ["version"]);
  const match = rawOutput.match(/aqtinstall\(aqt\)\s+v(\d+\.\d+\.\d+)/);
  return match ? compareVersions(match[1], ">=", "3.0.0") : false;
};

The problem is, if you point aqtsource at a branch on your Git repo, due to aqt's use of setuptools-scm, the version is auto-generated like v0.1.dev1823 so the regex doesn't match it due to the letters, and it falls to the : false expression of the ternary conditional operator. In my opinion that should be changed to : true to allow easier use with aqtsource.

Right now as you discovered, one either needs to pass extra: '--autodesktop', or only point aqtsource to a version tag that satisfies the version expectation. For example when I was testing some things with aqt, I created a fake version tag like v3.1.100 for use with aqtsource so that setuptools-scm would auto-assign it that version.

Indeed, I'll remove it from the README and such then. In the meantime I got it all working, as you can see in this workflow file of a project of mine. You can check the latest run here. You can use it right now if you need to, no need to wait for either PRs:

- name: Install Qt for host architecture
  uses: Kidev/[email protected]
  with:
    version: '6.8.1'
    host: 'all_os'
    target: 'wasm'
    arch: 'wasm_singlethread'
    set-env: 'true'
    modules: 'qtquick3d'
    aqtsource: 'git+https://github.com/Kidev/aqtinstall.git@wasm'
    extra: '--autodesktop'

@Kidev My application depends on Qt Quick, and this doesn't seem to properly install it for WASM or Android.

Failed to find required Qt component "Quick".

Here's my config:

- name: Install Qt (Host)
  uses: Kidev/[email protected]
  with:
    cache: on
    version: 6.8.1

- name: Install Qt (WASM)
  if: // ...
  uses: Kidev/[email protected]
  with:
    cache: on
    host: all_os
    target: wasm
    version: 6.8.1
    arch: wasm_singlethread
    set-env: true
    modules: 'qtquick3d'
    aqtsource: 'git+https://github.com/Kidev/aqtinstall.git@wasm'

Why is Quick not getting installed?

Actually, scrolling up, it can't find Qt core...

Found package configuration file:

    /.../lib/cmake/Qt6Quick/Qt6QuickConfig.cmake

  but it set Qt6Quick_FOUND to FALSE so package "Qt6Quick" is considered to
  be NOT FOUND.  Reason given by package:

  Qt6Quick could not be found because dependency Qt6Core could not be found.

...because it can't find Qt6CoreTools.

Found package configuration file:

    /.../lib/cmake/Qt6Core/Qt6CoreConfig.cmake

  but it set Qt6Core_FOUND to FALSE so package "Qt6Core" is considered to be
  NOT FOUND.  Reason given by package:

  Qt6Core could not be found because dependency Qt6CoreTools could not be
  found.

Nevermind, I had the wrong host paths set in my configure command.

The PR fixing WASM and more was merged into master and aqtinstall will soon release its version 3.2.0 including those changes. For it to work, I updated the default value of aqtversion to 3.2.*. I also updated the default value of version to the only Qt LTS version remaining (6.8.1). My temporary version of the Action is available here. Note the version v4.2.1 will only work once the release is published (I will update once it is the case). Until then you must still use v4.2.0.

- name: Install Qt for host architecture
  uses: Kidev/[email protected]
  with:
    version: '6.8.1'
    host: 'all_os'
    target: 'wasm'
    arch: 'wasm_singlethread'
    aqtsource: 'git+https://github.com/miurahr/aqtinstall.git'
    extra: '--autodesktop'

- name: Install Qt for host architecture
  uses: Kidev/[email protected]
  with:
    version: '6.8.1'
    host: 'all_os'
    target: 'wasm'
    arch: 'wasm_singlethread'

py7zr default could probably be bumped as well to ==0.22.* to coincide with aqtinstall/dependencies.

https://github.com/miurahr/aqtinstall/blob/master/pyproject.toml#L29

BTW: I have PR #267 Open for the python-version range, thoughts?

BTW: I have PR #267 Open for the python-version range, thoughts?

It is a good idea, I also have updated it in my latest update, along with py7zr.

It is not yet ready for this PR, still need some testing, but I'm working on getting commercial versions available to the installation using this Action (miurahr/aqtinstall#878 https://github.com/Kidev/install-qt-action). Here you can see a successful install of Qt using the use-commercial feature (note the install succeeds, but the workflow fails because as of today, addons are not yet supported by the use-commercial feature. It is work in progress though)

Added working support for Qt commercial.

You can see an example using my version of the workflow
It uses my version of install-qt-action (v4.4.2) while this PR is not merged

You can use it right now yourself like this, until this PR is merged:

- name: Install Qt
  uses: Kidev/[email protected]
  with:
    version: '6.8.1'
    target: 'desktop'
    arch: 'linux_gcc_64'
    aqtsource: 'git+https://github.com/miurahr/aqtinstall'
    use-commercial: true
    user: ${{ secrets.QT_USERNAME }}
    password: ${{ secrets.QT_PASSWORD }}
    modules: 'qtquick3d'

Fixed the issue after the re-sync, and some force push shenanigans to run the workflows on my repo too

Update: @jurplel almost all tests pass on my repo. There are issues with the windows-2019 runner however. I'm pretty sure it's because of MSVC2019, that is no longer supported by aqtinstall (see here for the discussion with the maintainer and other contributors of aqtinstall).

The commercial PR can be found here for more info.

@Kidev Will you be changing the YAML syntax (input parameter name) e.g. from use-commercial: true to use-official: true to match the recent naming change in aqtinstall? I'm just concerned that if this is merged/released now, and then the parameter name changes, that should be a new major version of this action since it breaks backwards compatibility.

Perhaps it's worth finalizing the YAML syntax now (even if it's still passing the old argument names to aqtinstall, since the renames haven't been released yet), or marking this as a draft if you'd rather wait for the next aqtinstall release, so there's no concern with the YAML backwards compatibility.

@Kidev Will you be changing the YAML syntax (input parameter name) e.g. from use-commercial: true to use-official: true to match the recent naming change in aqtinstall? I'm just concerned that if this is merged/released now, and then the parameter name changes, that should be a new major version of this action since it breaks backwards compatibility.

Perhaps it's worth finalizing the YAML syntax now (even if it's still passing the old argument names to aqtinstall, since the renames haven't been released yet), or marking this as a draft if you'd rather wait for the next aqtinstall release, so there's no concern with the YAML backwards compatibility.

That is a nice idea indeed, I would not have done that. I'm doing it right now along with the changes in commands to aqtinstall, been quite busy the last 2 weeks or so

@Kidev Will you be changing the YAML syntax (input parameter name) e.g. from use-commercial: true to use-official: true to match the recent naming change in aqtinstall? I'm just concerned that if this is merged/released now, and then the parameter name changes, that should be a new major version of this action since it breaks backwards compatibility.
Perhaps it's worth finalizing the YAML syntax now (even if it's still passing the old argument names to aqtinstall, since the renames haven't been released yet), or marking this as a draft if you'd rather wait for the next aqtinstall release, so there's no concern with the YAML backwards compatibility.

That is a nice idea indeed, I would not have done that. I'm doing it right now along with the changes in commands to aqtinstall, been quite busy the last 2 weeks or so

This sounds good to me—after CI is passing (which I believe it should do if you merge/rebase off of main), we should be good to merge this, then merge @jdpurcell's ARM64 hosts PR

This should be good, I'm testing on my repo as usual. Same as last time, it works on the official repo since my PR on aqtinstall was merged, BUT it is NOT YET RELEASED in a version. So adding this is required until it is the case:

aqtsource: 'git+https://github.com/miurahr/aqtinstall.git@master'

This should be good, I'm testing on my repo as usual. Same as last time, it works on the official repo since my PR on aqtinstall was merged, BUT it is NOT YET RELEASED in a version. So adding this is required until it is the case:

aqtsource: 'git+https://github.com/miurahr/aqtinstall.git@master'

I think we can merge soon but hold off on releasing this until the new aqtinstall version drops. I wish we had a way to test this, but I guess since it is a commercial version, there is not really an easy way since we need credentials...